Participating in LionWeb
Participation
The LionWeb team sees the participation of twelve developers, all with a long history in language engineering and modeling tools (listed in alphabetical order)
- Meinte Boersma, Freelancer, The Netherlands
- Norman Koester, itemis, Germany
- Sergej Koscejev, Freelancer, Czech Republic
- Sascha Lisson, itemis, Germany
- Pedro J. Molina, Metadev, Spain
- Eugen Schindler Canon Production Printing, The Netherlands
- Alex Shatalin, Jetbrains (MPS Team), Czech Republic
- Niko Stotz, F1RE, The Netherlands
- Ulyana Tikhonova, F1RE, The Netherlands
- Federico Tomassetti, Strumenta, Italy
- Markus Voelter, Freelancer, Germany
- Jos Warmer, openmodeling, The Netherlands
Join us on Slack for interesting discussions.
Activities
-
The main focus is the definition of protocols for the communication between participating software components such as repositories and clients. To make this feasible, we also define a meta-metamodel as well as a reference architecture.
-
Where appropriate, in order to support the protocols, LionWeb defines programming language-level APIs to access models and metamodels and to encapsulate the protocols.
-
A third activity is to create a collaboration hub for the developers of such components, to empower other software developers to develop web-based modeling solutions, and to educate the public about the benefits of this approach.
Work Products
We aim to create the following work products (in order of descending priority):
- [Document] Specifications for the communication protocols; this also requires the definition of a meta-metamodel
- [Document] A reference architecture for cloud-based modeling tools (necessarily mainly to be able to produce the others)
- [Code] Where appropriate, bindings for these protocols in several programming languages
- [Code] Reference implementations and examples of how to build systems using the LionWeb protocols (in particular, using some of the systems mentioned in the History section)
In terms of how we work, we aim for a collegial atmosphere and effective technical discussions. All our specifications will be backed by working code (OMG, this is really nice!).
This project will not provide production-quality implementations for the repositories or clients; we expect this to be done by the community, for example, based on the tools mentioned in the History section.